canon/tiers/01_Tier_1_Foundation/T1_Personal_Dimension_Spec [ACTIVE v1.1].md
This is a CONSOLIDATION of canon that already exists, not a design pass. Josh ruled it on 2026-08-04, verbatim: "We have already authored this in our canon and put many hours into it." The ruling is recorded in the head section of docs/spine/DECISIONS_PENDING_JOSH.md as D-PERSONAL-DIMENSION, and it supersedes that file's own earlier three-option brief on the same subject.
The Personal Dimension was never unauthored. It was UNGATHERED: its definition lives in T1_Ability_Tree, its realm law in T1_Vril_and_Magic_System_Master, its New Game Plus behaviour in T3_Familiars_Named, its creature layer in T3_Creatures_Tameable, its pipeline obligations in T1_Build_Pipeline_Contracts, its discipline row in T0_Hard_Lines, its care ruling in the governing realm care table, and its build grammar in the Josh-ruled Domains frame. This document brings those homes into one place and adds nothing to them.
Two further homes are PROPOSAL-TIER and are gathered here as proposals rather than as canon, because a consolidation that omitted them would leave the next wave re-deriving what already exists. base-building §5 designs this space as the unbounded integrity-visible sandbox, the breeding venue and the astral fast-travel hub, and its own worklist names the authoring of this spec as an open item [SRC: docs/proposals/systems/base-building.md # 5. Layer C — Personal Dimension: the unbounded, integrity-visible sandbox]. The WS7 wiring plan proposes a dwelling registry and seeds this space as row DW_0001, carrying reachability GLOBAL_ASTRAL, siting_rule unbounded_physics_free, integrity_visible full, creature_capacity_band housing_200plus_TBD_JOSH, fast_travel_node yes_astral_hub and hearthway_access_rule astral_anywhere [SRC: docs/proposals/systems/WS7_WIRING_BUILD_PLAN.md # NEW T0_Dwelling_Registry — owner base-building]. Nothing from either is asserted as canon in this document; where they touch a §10 silence, §10 names them.
The Personal Dimension is opened by DIMENSION POCKET, a Tier 6 Adeptus Minor ability on the Ether-Crown seat. Vril cost passive, cast pattern passive, persistence class permanent. It unlocks at Crown numerical 100 plus completion of the canonical Crown Adeptus Minor questline plus integrity-band canonical scaling per the mirrored five-band framework, and it "opens canonical access to a personal astral sub-space — the Personal Dimension" [SRC: T1_Ability_Tree # §11.7 Ether — Crown-seat].
The machine layer already carries the ability as row A_C_011, ability_class utility_dimension_access, mastery_point_cost 3, eam_pair_eligibility EAM-on-bonded-Crown, canonical_questline_ref Crown Adeptus Minor, whose description_brief reads "Personal Dimension access; 200+ creature housing + garden + integrity-visible home (defers spec to T1_Personal_Dimension_Spec)" [SRC: registries/T0_Ability_Tree_Registry # A_C_011].
Canon states three contents in the ability line and a fourth in two other homes.
The 200-plus figure is the only number canon attaches to this space. It is stated as a floor, and §10 records that no cap of any kind is stated anywhere.
The space is integrity-visible, and the ability line states the register in substrate terms: "L1 Truly Good protagonists access verdant-light substrate, L4-L5 Evil access shadow-substrate variants, L3 Drifting access neutral-grey balance state" [SRC: T1_Ability_Tree # §11.7 Ether — Crown-seat]. The governing realm care table states the same property from the care side, and states it across five: "Its only care surface is integrity-visibility across the five bands" [SRC: docs/pipeline_review/REALM_CARE_TIERING_2026-07-28.md # 11 — the Personal Dimension, ability-canon Tier 6 Dimension Pocket].
The L2 Good Enough band carries NO stated substrate register. Canon names L1, L3 and the L4-L5 pair and stops. That is a real gap between a four-value statement and a five-band property, and it is declared at §10 rather than filled here.
The axis itself is already minted. AX_11 integrity_band, axis_kind gate, closed vocabulary, cardinality 5 ruled, applies_to_families "ability;equipment;personal_dimension", records in its own notes that the axis "gates rather than multiplies for abilities, and multiplies (as an asset-variant axis) for the Personal Dimension" [SRC: registries/T0_Item_Axis_Registry # AX_11]. Section 8 answers what that multiplication is made of.
HL_0118 carries the system as a DISCIPLINE-severity row applying to the UE5, Quest and Region pipelines at the post-book-processing chapter range, cross-referencing HL_0023, the integrity-appearance hard line [SRC: registries/T0_Hard_Lines # HL_0118].
FINDING FOR THE DIRECTOR, reported and not repaired by this pass. HL_0118's source_section cell reads "T1_Vril §12.4". Section 12.4 of the live T1_Vril_and_Magic_System_Master is "Show-don't-tell hard lines (Grand Sage spoiler)" and carries no Personal Dimension content; the live T1_Vril home for this system is §1.2.6, the invented-realm rider [SRC: T1_Vril_and_Magic_System_Master # 1.2.6 The invented-realm rider]. The pointer is stale. Repairing it edits a T0 hard-line row and shifts the fidelity baseline, so it is surfaced to the director rather than applied here.
The CVD carries ZERO occurrences of "personal dimension", "dimension pocket", "astral sub-space", "menagerie", "garden" and "creature housing". The same file carries "Crown" three times, "Chao" twice, "completionist" six times, "base Domains" once and "max upgrade" once, so the search can match. The Personal Dimension is therefore NOT CVD-level canon: it is T1 ability canon plus a T1 realm rider plus a T3 ruling plus a T0 discipline row. That measured fact bounds what this document may claim, and it is why §8 is scoped to an architecture question rather than to world canon.
T1_Vril places this space inside realm doctrine: "The same rider covers the Personal Dimension, the one realm whose law the PLAYER writes rather than visits: a personal astral sub-space opened by the Tier 6 Ether-Crown passive, free of growth-rate and terrain-stability constraint, and visible across the integrity bands. Its law is authored under this section with the same scoped provenance exemption... It remains proposal-tier here and its spec is owned elsewhere" [SRC: T1_Vril_and_Magic_System_Master # 1.2.6 The invented-realm rider].
Three consequences follow from that placement, all of them already ruled in the section that hosts it.
The realm care table is PROPOSAL-TIER in its own status line, and is made GOVERNING for care tier and duty by the realm-law section that hosts the roster; only its two-value care_tier enum is ratified. Read at that tier, it sets care_tier standard and duty NONE for this space, on the stated reasoning that this is a "player-authored pocket space, no source tradition", generation_class invented, source_corpus_state not applicable; the art fan-out MAY raw-generate freely and MAY NOT do anything beyond the standing rules. The row exists so the provenance tooth has a DECLARED EXEMPT row rather than a silent skip [SRC: docs/pipeline_review/REALM_CARE_TIERING_2026-07-28.md # 11 — the Personal Dimension, ability-canon Tier 6 Dimension Pocket]. That table is the governing surface for per-realm care and outranks prose elsewhere by the ruling of the doc that hosts it [SRC: T1_Vril_and_Magic_System_Master # 1.2.7 Provenance, tier, and scope].
This is the one realm in the roster whose care surface is a MECHANIC rather than a tradition. Everything §17.1 protects lives outside this space by construction, because nothing inside it belongs to anyone but the player.
T0_Realm_Ruleset_Registry holds eleven rows, RLM_0000 the human-world baseline through RLM_0010 the fairy realm. A twelfth row for the Personal Dimension is PROPOSED and not minted [SRC: docs/pipeline_review/HOLLOW_ADMISSION_BRIEF_2026-07-27.md # 1. The roster is an ENUMERATED CLOSED LIST]. Measured: RLM_0011 and RLM_0012 occur in three files, all of them review documents, and in no registry; RLM_0010 occurs in nine files, so the search can match. Whether this space takes a ruleset row is declared open at §10, because the roster count is that registry's own completeness claim and minting into it is a schema act rather than a consolidation act.
Access gates at the Crown Adeptus Minor questline [SRC: T1_Ability_Tree # §11.7 Ether — Crown-seat]. The Crown seat is one of the three forced Ether bindings and is acquired at Ch 15 Egypt, so Ch 15 is a floor and not the unlock: the questline plus Crown numerical 100 sit well beyond it [SRC: T1_Ability_Tree # §11.7 Ether — Crown-seat]. The system is therefore entirely outside the Prologue-through-Ch-13 slice, which is why authoring it now costs the slice nothing and blocks nothing in it.
ITEM RIFT is a Tier 4 Practicus Crown ability unlocking at the Ch 15 Egypt tomb-artifact activation, low vril cost, by which "the protagonist accesses a vril-folded inventory pocket — a personal storage dimension allowing item retrieval and storage across regions", and it is the canonical inventory mechanic [SRC: T1_Ability_Tree # §11.7 Ether — Crown-seat]. It is stated as INVENTORY. Dimension Pocket at Tier 6 is stated as a PLACE, with housing, garden, training and construction. Both are Crown, both are pockets, and they are two abilities two tiers apart with two different jobs. No canon anywhere merges them, and this document does not.
The practical consequence for build: Item Rift is the storage surface reachable from Ch 15 onward and carries the inventory screen; the Personal Dimension is a streamed sub-space reachable only after the Crown Adeptus Minor questline and carries its own screen per §9. Poison reagents storing in "Item Rift inventory" is the ability tree's own worked example of the split [SRC: T1_Ability_Tree # §11.9 Poison — Trade 4 Herbalism plus Trade 5 Alchemy].
The pipeline contract lists "Personal Dimension astral sub-space streaming" in the World Partition and Streaming scope, beside chapter loading, indoor and underground sub-region streaming, the Ch 66 through 69 mythological realm streaming, and Tier B DLC content [SRC: T1_Build_Pipeline_Contracts # 1.2 UE5 System Architecture]. World Partition reads T0_Chapter_Index and T0_Region_Index and references this spec; PCG likewise references this spec alongside T1_World_Geography_Master and T1_RNG_Sigma_Constraint_System [SRC: T1_Build_Pipeline_Contracts # 1.2 UE5 System Architecture]. The space is thus already typed as a first-class streamed level rather than as a menu.
Canon carries TWO husbandry and training venues and does not collapse them.
The compounds are the early, distributed, trade-rooted venue that arrives with the trades; the Dimension is the late, unified, unbounded one that arrives with the Crown. The distinction is a progression rather than a duplication, and neither replaces the other.
Bond-lite taming puts TAME-status species at Chao Garden passive companion tier. These bonds occupy no combat familiar slot, do not reach twelve-tier Hermetic bond mastery, and do not trigger legendary evolutions; a player may hold dozens across Ground, Flying, Water, aquatic-insect and micro-ecology categories without touching the three active familiar slots [SRC: T3_Creatures_Tameable # 1.3 Encounter mechanics — wild spawn, observation, taming, combat avoidance]. The 22 named familiars are a different population, with bond questlines, three simultaneous active slots, evolutions and legendary forms [SRC: T3_Familiars_Named # §1.1 The 21-plus-1 Architecture].
That boundary is what §6 turns on. Creatures cross the New Game Plus line and familiars do not, and the reason is the questline.
Monster breeding is an L1 everyone-plays single-player husbandry loop on the 400-plus ordinary tameable roster, never on the 22 named familiars. The firewall is load-bearing and absolute: bred offspring are always ordinary-tier, never a legendary-tier species, never a 22-slot familiar occupant, never a canonical evolution; a bonded legendary may sire only an ordinary prestige line with a flavour name and a minor trait halo [SRC: T3_Familiars_Named # §1.7 Familiar Garden Raising System] [SRC: T3_Creatures_Tameable # 1.4 Chao Garden passive companion framework]. The CVD reconciles the same firewall at the numerical-canon layer [SRC: T1_CVD_Creative_Vision_Document # 17.12 Cardinal numerical canon]. Breeding tournaments, cross-lineage and cross-realm breeding, and cross-compound migration remain the Tier C MMO superset [SRC: T3_Creatures_Tameable # 1.4 Chao Garden passive companion framework].
Numerical husbandry parameters are recorded by their own canon as pending authorial assignment [SRC: T3_Creatures_Tameable # 1.4 Chao Garden passive companion framework]. This document does not assign them.
The Josh-ruled Domains addendum gives the space a live combat function through deployment physics keyed to a vehicle's medium and speed: water familiars fight in and around a hull on water and retreat to the Personal Dimension on the Vimana; flying familiars wheel around a stalled or slow craft but cannot keep up at speed and retreat to the Personal Dimension, re-emerging when the craft is slow or idle; ground familiars ride and guard and retreat to the Dimension at high speed or in the air [SRC: docs/proposals/DOMAINS_VEHICLES_AND_ENRICHMENT_BACKLOG.md # §9b — Companion & Creature Command / Deployment / Dispatch (Josh 2026-07-10 addendum)]. The frame is Josh-ruled; the document carrying it is proposal-tier and says so, so the deployment matrix lands here as RULED DIRECTION whose data shape is unbuilt.
The buildable and ownable spaces are ONE meta-system, ruled unified by Josh on 2026-07-10. The Personal Dimension is "your private world (Minecraft/DQB2-style build; familiars live + are bred here)"; the Watercraft is the sea domain; the Vimana is the sky domain; the ten trade home-bases are the fixed workshops, locked at HL_0033 and untouched. The shared spine is one build and upgrade grammar of trade-crafted modules, familiars housed in the Personal Dimension and carried as mobile crew on the Watercraft and the Vimana, and the L1-fun, L2-real-technique, L3-metaphysics layering on every domain [SRC: docs/proposals/DOMAINS_VEHICLES_AND_ENRICHMENT_BACKLOG.md # §1 — The unifying frame: "Domains & Vehicles" (Josh ruling: UNIFIED)].
The vehicle design reads the same grammar from the other end: customization runs on "the unified Domains build grammar (the same grammar as the Personal Dimension)" [SRC: docs/proposals/systems/vehicles-fleets.md # 4]. The CVD reaches the same grammar by name from the device-count side, ruling that the Vimana's promotion to a buildable home-base is "the same single Vimana craft upgraded on the Domains build grammar" and adds no eighth device [SRC: T1_CVD_Creative_Vision_Document # 19.5 May 5, 2026 — Progressive-Acquisition Device Mechanic Refinement]. So the grammar itself is CVD-acknowledged even though the space is not.
The MINECRAFT AND DQB2 REGISTER is the load-bearing half of this frame for §8, because a free-building register means the contents of the space are minted by the player at runtime rather than authored as a fixed set. Its attribution is stated precisely, because §8 leans on it. The 2026-07-10 Domains ruling that Josh is recorded as making is the UNIFICATION — that the buildable spaces are one meta-system — and the Minecraft and DQB2 phrasing there sits in that proposal-tier document's own table rather than in the enumerated ruling list [SRC: docs/proposals/DOMAINS_VEHICLES_AND_ENRICHMENT_BACKLOG.md # §10 — Provenance]. The REGISTER is Josh-ruled separately and verbatim on 2026-08-04, where the comparator bar names the teacher per system and the binding read records "building (Personal Dimension/Domains) = DQB2/Minecraft", with the bar set at EXCEEDING that teacher rather than matching it [SRC: docs/FACTORY_CONTINUATION.md # JOSH RULING 2026-08-04 ~20:10 (VERBATIM, ANGRY — THE FUN PANTHEON IS THE BUILD BAR)]. That is the citation §8.3 rests on.
The CVD's cardinal numerical canon names two L2 completion conditions: "max upgrades on every craft (the Vehicle/Mount and base Domains buildables) and top score on every minigame" [SRC: T1_CVD_Creative_Vision_Document # 17.12 Cardinal numerical canon]. Measured: the word Domains reaches the CVD exactly twice. Once here, as a completion condition at §17.12, and once at §19.5, where the Vimana's buildable promotion runs on "the Domains build grammar" per §5.1. Both occurrences are of the GRAMMAR and the completion condition, and neither names the Personal Dimension itself — which is the §1.5 measurement stated from the other side. The Personal Dimension is therefore load-bearing for one-hundred-percent completion rather than optional flavour, even though the CVD never names the space.
The layer model places it precisely: Layer 2 is the completionist who wants to "max every skill, top-score every minigame, fully upgrade every vehicle and base, complete every side quest" [SRC: T1_CVD_Creative_Vision_Document # §2. CORE THESIS — CONSCIOUSNESS AS SUBSTRATE].
Canon states that ONE grammar is shared and that the register is free building. It does not state the module list, the placement rules, the plot or build grid, the snapping model, or any budget. Those are declared open at §10 — with the note, carried there, that a proposal-tier grammar for exactly those surfaces already exists at base-building §4.3 and a proposal-tier schema field already seeds it. Neither is ratified here, and this document does not promote either.
Everything in this section is Josh-ruled on 2026-07-30, the twenty-ninth sitting, and is carried verbatim in substance from the owning canon [SRC: T3_Familiars_Named # §5.11 New Game Plus and the Post-Game Epilogue — the Twenty-Ninth Sitting Canon].
TAMED CREATURES CARRY, through the Personal Dimension, and nobody re-tames a built collection. At the moment the Personal Dimension unlocks in New Game Plus it arrives as a TRANSFER of the previous playthrough's dimension: the tamed-creature menagerie and all the invested dimension-world state come across intact. Josh's recorded reason is the investment itself, because the completionist does not do it all over again and the hours in that dimension are the thing being carried [SRC: T3_Familiars_Named # §5.11 New Game Plus and the Post-Game Epilogue — the Twenty-Ninth Sitting Canon].
The transfer arrives AT THE UNLOCK, not at the New Game Plus boundary. The dimension is gated by its own access, the Crown Adeptus Minor Dimension Pocket ability, so the early run is played without it exactly as a first playthrough is [SRC: T3_Familiars_Named # §5.11 New Game Plus and the Post-Game Epilogue — the Twenty-Ninth Sitting Canon].
Scaling at the unlock is DOWN ONLY, and it governs the transferred creatures. Everything above the player's current level is scaled back to that level at the unlock moment, and anything already below their level stays at its lower level. Nothing is scaled up [SRC: T3_Familiars_Named # §5.11 New Game Plus and the Post-Game Epilogue — the Twenty-Ninth Sitting Canon].
BONDED FAMILIARS DO NOT CARRY. Every familiar bond is earned through its bonding questline in New Game Plus exactly as in the base game, because a bond that arrives without its questline is not a bond but an inventory row [SRC: T3_Familiars_Named # §5.11 New Game Plus and the Post-Game Epilogue — the Twenty-Ninth Sitting Canon]. The transfer therefore carries a POPULATION and not a roster: dimension-world state and tamed creatures cross, familiar bonds re-form through play.
The owning canon records these as named and unresolved, and this document neither resolves nor widens them.
The connective-web inventory frames the endgame free-play venue as the RECLAIMED Personal Dimension answering the birthright ceiling stripped at the rift fall, tagged EXISTS_UNPAID [SRC: docs/proposals/WHOLE_ARC_CONNECTIVE_WEB_INVENTORY.md # ECV-09]. The Ch 1 node carries the origin half of that ring with no forward hint [SRC: docs/spine/CH_01.md # Entry header, arc_state]. The Epilogue node considered the link and DECLINED to type it, on the stated ground that the live entry does not itself ground the endgame sandbox in the birthright-home framing and that typing it would author new canon [SRC: docs/spine/CH_EPILOGUE.md # Decisions, Q11].
Measured: across 80 live spine nodes the Personal Dimension is named in exactly two, CH_01 and CH_EPILOGUE, counting the hyphenated form, which is the only form CH_EPILOGUE uses and the reason this count is two rather than the one the promise-ledger row records per §10. The CH_EPILOGUE mention is that declining decision rather than a staged scene; the control term "vril" appears in all 80. The reading stays proposal-tier and this document does not promote it.
The Marriage and Partnership system is recovered canon from Josh's pre-Claude GDD, classed RECOVERED-NEW with "natural home = T1_Personal_Dimension_Spec" and ranked the single highest-value recovery in that reconciliation [SRC: docs/original_predclaude/INGEST_GDD.md # Recommended actions — the recoverable set (ranked)]. It has had no home in the corpus since. It is consolidated here because that is where its own reconciliation routed it, and it is carried as RECOVERED SUBSTRATE at proposal tier rather than asserted as ratified system canon.
The player may enter partnership arrangements with NPCs and with other players. The NPC half is Tier A and is this spec's scope; the other-players half is Tier C, where the private-instance solo layer of Tier A ends and multiplayer is owned [SRC: T1_Tier_C_MMO_Spec # §3.1 Tier A Solo Base], and the reconciliation that routed this system here routes its multiplayer siblings there by the same sorting [SRC: docs/original_predclaude/INGEST_GDD.md # §10 — World & Environment]. Multiple partnership structures are available: SOLO PARTNERSHIP, EQUAL SHARED PARTNERSHIP, PRIMARY AND SECONDARY, INDIVIDUAL WITH OVERLAP, and SEQUENTIAL MEMORY ARRANGEMENTS. The system is designed without prescribing which arrangement is correct [SRC: docs/original_predclaude/extracted/GDD_Humanity_Game_Complete.md # 10.5 Marriage and Partnership System].
The non-prescription is the design rather than an omission, and it matches the arc's whole posture on choice: the game reports what a player chose and does not rank it.
Breakup negotiation is a FUNCTIONAL MECHANIC rather than a simple end state. Three restoration options exist: returning to just before the relationship began, returning to a significant milestone within it, or maintaining the current state with adjusted terms [SRC: docs/original_predclaude/extracted/GDD_Humanity_Game_Complete.md # 10.5 Marriage and Partnership System].
Best friends receive an IDENTICAL system to romantic partners [SRC: docs/original_predclaude/extracted/GDD_Humanity_Game_Complete.md # 10.5 Marriage and Partnership System]. That parity composes with the ruled best-friend canon elsewhere in the arc, where the Ch 1 best-friend selection is already a load-bearing choice.
Canon states the system and states this spec as its home. Canon does NOT state how the system ATTACHES to the space: whether a partner resides in the Dimension, whether residency is what the arrangements express, whether the arrangement surfaces on a Dimension screen or a relationship screen, or whether the three restoration options touch dimension state at all. Measured at §10 with its control. The attachment is declared open.
Five separate blocks of T1_Build_Pipeline_Contracts, one per production channel, defer the same question to this spec by name. Each sits under an "Items resolving at Personal Dimension spec populate" heading in its channel's Open Items section, and each asks whether per-integrity variants live as SEPARATE IDS or as a RUNTIME OVERRIDE off a single base [SRC: T1_Build_Pipeline_Contracts # 2.11 Open Items at Contract Lock] [SRC: T1_Build_Pipeline_Contracts # 3.11 Open Items at Contract Lock] [SRC: T1_Build_Pipeline_Contracts # 4.11 Open Items at Contract Lock] [SRC: T1_Build_Pipeline_Contracts # 5.11 Open Items at Contract Lock] [SRC: T1_Build_Pipeline_Contracts # 6.11 Open Items at Contract Lock]. The same question is mirrored in the item-axis registry, whose AX_11 notes record that the integrity band "multiplies (as an asset-variant axis) for the Personal Dimension" and that the decision is stalled on this spec [SRC: registries/T0_Item_Axis_Registry # AX_11].
ONE BASE ASSET PER THING, AND ONE PER-BAND RUNTIME OVERRIDE LAYER PER CHANNEL, DECLARED AT THE REALM AND APPLIED OVER EVERYTHING INSIDE IT. Per-integrity asset ids are the wrong shape for this space, and the override is the shape canon's own words already describe.
Six anchors, each harvested rather than reasoned from taste.
Each channel keeps ONE id and gains ONE band-keyed override, read at runtime from the live integrity score.
The override reads WS_001 integrity_score, the continuous integrity signal whose declared consumers already include the appearance renderer and the voice generation layer [SRC: registries/T0_Worldstate_Variables # WS_001], and resolves the band through the AX_11 closed five-band vocabulary [SRC: registries/T0_Item_Axis_Registry # AX_11] — which is the derived WS_002 integrity_level enum, so no new variable is minted here [SRC: registries/T0_Worldstate_Variables # WS_002]. Naming that key is a deliberate act rather than an oversight: the audio translation layer reached this same surface and declined to bind a WS_NNN key to it under its own ws.* discipline, leaving the binding to the owning spec [SRC: docs/translation/T99_Translation_Audio.md # Music Step 6 — MetaSounds adaptive graph wiring]. This section is that owning spec, so the binding is made here in the open rather than crossed silently. Because canon assigns registers to L1, L3 and the L4-L5 pair and leaves L2 unstated per §1.3, the override table ships with the L2 row DECLARED EMPTY and visible rather than silently defaulted, so the gap stays legible every run until it is ruled.
Where a Personal-Dimension surface is a CANONICAL, author-in-loop, hero-tier artifact, meaning a scripted set-piece scene or a hard-line quest staged inside the space, the existing canonical-track discipline governs and per-id rows are correct, exactly as the contracts already say for the canonical sets. The override rule governs the ambient, player-authored body of the space.
Today that body is the whole space. Measured: no live spine node stages a Personal-Dimension scene, quest or beat; the phrase occurs in exactly two of 80 nodes and both occurrences are connective-ring bookkeeping rather than staged content, against a control of 80 out of 80 for "vril". The carve-out is therefore an empty set at authoring time, and it exists so that a later canonical set piece does not have to argue with this section.
THE OBJECTION, stated at full strength and already on the record: answering the variant question in isolation fixes the asset architecture before the system it serves exists, and an architecture chosen against a partly-unauthored system can be the wrong one [SRC: docs/spine/DECISIONS_PENDING_JOSH.md # D-PERSONAL-DIMENSION — the system Josh named, whose spec is two lines].
THE ANSWER IS THAT THE OVERRIDE IS THE REVERSIBLE DIRECTION. A base asset plus a band-keyed override table can be BAKED into per-band ids later by a mechanical build-time pass, because every input that bake needs is already declared. The reverse does not hold: five authored id sets cannot be un-forked into one without discarding four sets of authored work. When a system is partly unauthored, the correct architecture is the one that can still become the other one, and that is the override. This section is scoped to the one blocked question, reaches nothing else, and is explicitly REVERSIBLE on a later ruling.
The Personal Dimension is one of five GAME-NATIVE screens that carry real information-architecture design work, alongside the Rune Forge, the Grimoire, imprint crafting and the familiar roster; the rest of the screen roster is standard-by-default and needs no ruling to enumerate [SRC: docs/GENRE_BASELINE.md # the screen-roster entry]. The screen's own information architecture is unauthored and is declared at §10. Naming it here records the obligation so the UI wave has a denominator.
Each entry is an OPEN DESIGN SURFACE rather than a defect, and each carries the control that proves the probe could have matched. The probe scope is the 764-file canon-and-docs corpus of _source, docs, registries and the repo root.
T0_Dwelling_Registry — owner base-building] [SRC: docs/proposals/systems/base-building.md # 5. Layer C — Personal Dimension: the unbounded, integrity-visible sandbox]. Unbounded is a stated DIRECTION at proposal tier, not a ratified extent, and no canon file dimensions the space. Control: the same vocabulary occurs in 70 files, 149 occurrences, corpus-wide.T0_Dwelling_Registry — owner base-building]. That document's own worklist still carries the module catalog and the snapping rules as unbuilt. So the silence is a RATIFICATION silence, not an authoring vacuum, and a later build wave should start from that proposal rather than re-derive one. Control: the same build vocabulary occurs in 16 files corpus-wide.